home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000290_news@newsmaster….columbia.edu _Thu Mar 12 13:34:50 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA29533
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 12 Mar 1998 13:34:50 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA28963
for kermit.misc@watsun; Thu, 12 Mar 1998 13:34:50 -0500 (EST)
Path: news.columbia.edu!panix!logbridge.uoregon.edu!europa.clark.net!169.207.30.81!newsfeeds.sol.net!newsops.execpc.com!posts.execpc.com!gotham-globe.newsops.execpc.com!usenet
From: manning@execpc.com (Steve Manning)
Newsgroups: comp.protocols.kermit.misc
Subject: K95 questions on SCOANSI
Date: Thu, 12 Mar 1998 18:10:19 GMT
Organization: Exec-PC BBS Internet - Milwaukee, WI
Lines: 34
Message-ID: <6e98bt$f4u@newsops.execpc.com>
Reply-To: manning@execpc.com
NNTP-Posting-Host: aston-1.mdm.mke.execpc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: gotham-globe.newsops.execpc.com 889726141 15518 (None) 169.207.85.1
X-Complaints-To: abuse@execpc.com
X-Newsreader: Forte Agent 1.5/32.451
Xref: news.columbia.edu comp.protocols.kermit.misc:8485
We're using K95 1.1.15.
When using the SCOANSI terminal type, if I don't set TELNET
TERMINAL-TYPE to ANSI, when I connect to an SCO OpenServer 5.0.4
system, K95 negotiates itself to H19(!). I read the info in BUGS.TXT
on setting TERMINAL-TYPE and CHARACTER-SET with the SCOANSI term type,
so I was able to get it working.
1. Why does it negotiate to H19 of all things?
2. The actual SCO console supports color, but am unable to get the
SCOANSI emulation to display color. Does color work with SCOANSI?
I'm also having a problem in a specific application when I use the
AT386 emulation. When the application starts up, it is clearing the
screen with spaces (ugh), but it has kicked into alternate character
set mode first, so all the spaces come out as accented "a"'s.
When I sit down at the console of one of our NCR SVR4 systems, which
allege to be "at386" too, and rlogin over to the SCO box where the
application lives, the screen appears to clear normally. Any ideas
why I'm seeing this behaviour or how to correct it?
I've captured the output of the rlogin session with truss, and I'll be
going over the escape sequences to try to figure out what is causing
the discrepancy. That'll probably take a while, and I don't have an
"AT386" spec that I can refer to, so if anyone has insights I'd sure
appreciate 'em.
Steve Manning
System Administrator
Mega Marts Inc.
Milwaukee, WI USA
manning@execpc.com